Efficient operation of relay nodes in a citizen broadband radio service (cbrs) network

ABSTRACT

Presented herein are methodologies for managing a citizens broadband radio service (CBRS) network. The methodology includes at a spectrum access system (SAS), receiving, from a Donor CBRS base station device (CBSD), a registration request, the registration request including capabilities information about a CBRS Relay Node with which the Donor CBSD communicates, in response to the registration request, sending, from the SAS to the Donor CBSD, a registration response indicating successful registration of the CBRS Relay Node, in response to the registration response, receiving via the Donor CBSD a spectrum enquiry message from the CBRS Relay Node seeking a channel allocation from the SAS, and in response to the spectrum enquiry message, sending from the SAS, and via the Donor CBSD, a resource grant response to the CBRS Relay Node, wherein the resource grant response includes an allocated channel and a maximum EIRP for the allocated channel.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.16/678,539, filed Nov. 8, 2019, the subject matter of which isincorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to the operation of a Citizen BroadbandRadio Service network, and particularly to managing relay nodes in sucha network.

BACKGROUND

Citizen Broadband Radio Service (CBRS) is a 150 MHz wide broadcast bandin the 3550-3700 MHz frequency range, time division-long term evolution(TD-LTE) band 48. Access to spectrum in the CBRS band is through the useof a Spectrum Access System (SAS), which protects incumbents frominterference from lower tier priority access license (PAL) and generalauthorized access (GAA) users, and protects PAL users from interferencefrom other PAL users and GAA users. The SAS maintains a database ofspectrum usage (by incumbent, PAL, and GAA users) in all census tracts(or areas) and allocates channels to CBRS Base Station Devices (CBSDs)(i.e., access points (APs)) using variety of rules including thefollowing.

Tier 1 users: incumbents (such as navy ships, military radars and fixedsatellite service earth stations) are allowed access to all thechannels.

Tier 2 users: PAL users are granted access in the 3550-3650 MHz band andare allowed to use a maximum of 7 10 MHz channels in a census tract (oran area). No licensee can take more than 4 PAL channels in a censustract.

Tier 3 users: GAA users are allowed access to all the channels but onlythe ones not being used by above users.

The SAS may consider multiple factors (such as those above) to determineappropriate spectrum allocation, and, in turn, informs CBSDs ofoperating parameters (such as frequency band or channel, and maximumEffective Isotropic Radiated Power (EIRP)) that the CBSDs can use (i.e.,to employ with User Equipment (UE)) at a given point in time. In someimplementations, CBSDs, CBRS client devices (e.g., CBRS UEs), and anEvolved Packet Core (EPC) may be deployed as part of a privateenterprise. Such a deployment can present several challenges, dependingon the topology.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a CBRS network topology and resource allocation logic inaccordance with an example embodiment.

FIG. 2 is a ladder diagram depicting a series of operations forallocating resources to a CBSD of a CBRS RN in accordance with anexample embodiment.

FIG. 3 is a ladder diagram depicting a series of operations for ascenario in which a SAS changes allocated resources for a CBRS when CBRSRNs are active in the network in accordance with an example embodiment.

FIG. 4 is a flow chart depicting a series of operations for handlingchannel changes for a CBSD that communicates with CBRS RNs in accordancewith an example embodiment.

FIG. 5 is a ladder diagram depicting a series of operations for ascenario in which a SAS changes allocated resources for a Donor CBRS anda CBRS RN in accordance with an example embodiment.

FIG. 6 is a flow chart depicting a series of operations for handlingchannel changes for a CBRS RN in accordance with an example embodiment.

FIG. 7 is a ladder diagram depicting a series of operations for ascenario in which a SAS changes allocated resources for a given CBRS RNin accordance with an example embodiment.

FIG. 8 shows a CBRS network topology that leverages a digital networkapplication controller (DNA-C) to provide resource allocation logic inaccordance with an example embodiment.

FIG. 9 shows a CBRS network topology that leverages a DNA-C to provideadditional resource allocation logic in accordance with an exampleembodiment.

FIG. 10 is a flow chart depicting a series of operations for allocatingresources in a CBRS network having CBRS RNs in accordance with anexample embodiment.

FIG. 11 depicts a device (e.g., a SAS or external controller) thatexecutes resource allocation logic in accordance with an exampleembodiment.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

Presented herein are methodologies for managing a citizens broadbandradio service (CBRS) network. The methodology includes at a spectrumaccess system (SAS), receiving, from a Donor CBRS base station device(CBSD), a registration request, the registration request includingcapabilities information about a CBRS Relay Node with which the DonorCBSD communicates, in response to the registration request, sending,from the SAS to the Donor CBSD, a registration response indicatingsuccessful registration of the CBRS Relay Node, in response to theregistration response, receiving via the Donor CBSD a spectrum enquirymessage from the CBRS Relay Node seeking a channel allocation from theSAS, and in response to the spectrum enquiry message, sending from theSAS, and via the Donor CBSD, a resource grant response to the CBRS RelayNode, wherein the resource grant response includes an allocated channeland a maximum Equivalent Isotropically Radiated Power (EIRP) for theallocated channel.

A device or apparatus is also described. The device may be a SAS, orsome other device. The device may include an interface unit configuredto enable network communications, a memory, and one or more processorscoupled to the interface unit and the memory, and configured to:receive, from a Donor citizens broadband radio service (CBRS) basestation device (CBSD), a registration request, the registration requestincluding capabilities information about a CBRS Relay Node with whichthe Donor CBSD communicates, in response to the registration request,send to the Donor CBSD, a registration response indicating successfulregistration of the CBRS Relay Node, in response to the registrationresponse, receive via the Donor CBSD a spectrum enquiry message from theCBRS Relay Node seeking a channel allocation, and in response to thespectrum enquiry message, send, via the Donor CBSD, a resource grantresponse to the CBRS Relay Node, wherein the resource grant responseincludes an allocated channel and a maximum Equivalent IsotropicallyRadiated Power (EIRP) for the allocated channel.

Example Embodiments

FIG. 1 shows a CBRS network topology and resource allocation logic inaccordance with an example embodiment. As shown, the topology 100includes a spectrum access system (SAS) 110 that hosts resourceallocation logic 105, a Donor CBRS Base Station Device (CBSD) z 150, aCBRS scheduler 152, a CBRS relay node (RN)×160, a CBRS RN y 170, CBRSUEs 154, CBRS UEs x1, x2, x3 and CBRS UE y1. CBRS RN x 160 includes aCBRS UE x function 161 to communicate with Donor CBSD z 150, and a CBSDx function 162 to communicate with CBRS UEs x1, x2, x3. CBRS RN x 170includes a CBRS UE y function 171 to communicate with Donor CBSD z 150,and a CBSD y function 172 to communicate with CBRS UE y1. CBRS scheduler152 is responsible for receiving an indication of available channel andmaximum EIRP information from SAS 110 and allocating the same directlyto CBRS UEs 154, and to CBRS RN x 160 and to CBRS RN y 170, in the formof physical resource blocks (PRBs). In turn, CBRS RN x 160 and CBRS RN y170 allocate spectrum resources to CBRS UEs x1, x2, x3 and y1,respectively. As will be explained more fully below, resource allocationlogic 105 determines how best to allocate channels to network elementssuch as Donor CBSD z 150 and CBRS RNs in the network.

As those skilled in the art will appreciate, CBRS RNs are used toprovide enhanced coverage and capacity (e.g., at cell edges). It shouldbe noted that the CBRS RNs described herein are different from, e.g., arepeater in that the described CBRS RNs are configured to demodulate anddecode received data, perform LTE (CBRS) protocol processing, and thentransmit a new signal. Two types of CBRS RNs may be deployed in thecontext of the embodiments described herein: an “inband relay” and an“outband relay.”

With an inband relay, both air-interfaces of the CBRS RN use the samefrequency. If a given CBRS RN uses the same frequency on both of itsair-interfaces simultaneously, there may be higher interference at thatCBRS RN. One way to address this issue is to implement time divisionmultiplexing at the CBRS RN where some time slices are used for the CBRSUE interface (e.g., 161, 171) for communication with Donor CBSD z 150,and some other time slices are used for the CBSD interface of the RN(e.g., 162, 172)). In such a configuration, a CBRS RN works in ahalf-duplex (HD) mode. Another way to address interference associatedwith an inband relay is to transmit and receive at the same time, usingincreased isolation between the respective transmit and receiveantennas. In such a configuration, the CBRS RN works in a full-duplex(FD) mode, but this is typically a more costly implementation.

With an outband relay, the air-interfaces of the CBRS RN use differentfrequencies. Such an outband RN operates in FD mode, and is easier todeploy and operate.

There are several additional categorizations of CBRS RNs, as follows:

Type I LTE relay: These LTE relays control their cells with their ownidentity including the transmission of their own synchronizationchannels and reference symbols. Type 1 relays appear as if they are aCBSD to UEs.

Basic Type 1 LTE RN provides half duplex with inband transmissions.

Type 1.a: outband RN, which can transmit and receive at the same time(i.e., FD RNs); and

Type 1.b: inband RN, which provides sufficient isolation between itstransmit and receive antennas. Such RNs have potentially higher cost,but do operate in FD mode.

Type 2 LTE RN: These LTE RNs do not have their own cell identity andlook just like a main cell. Any UE in range is not able to distinguish arelay from a main eNodeB (i.e., Donor CBSD) within the cell. Controlinformation can be transmitted from the Donor CBSD and user data fromthe LTE relay.

With reference again to FIG. 1, and in view of the foregoing definitionsand categorizations, certain limitations of CBRS RNs may become evident.

I) In FIG. 1, SAS 110 allocates resources (such as spectrum, max EIRP, .. . ) for Donor CBSD z 150 to which it is connected, but SAS 110 may notbe configured to allocate any resources for CBRS RN x 160 or CBRS RN y170.

Note that it is unlikely that CBRS RN x 160 or CBRS RN y 170 would beconnected via a wired interface to SAS 110.

II) As noted above, there may be different types of CBRS RNs deployed ina private enterprise including Type I, Type II, inband/outband,half-duplex/full-duplex CBRS RNs. SAS 110 is unlikely to have knowledgeof individual devices in a given private enterprise deployment, leadingto multiple possible issues.

III) With LTE-TDD (time division duplex), an LTE base station uses a TDDformat that consists of a pattern of slots for downlink (DL) and uplink(UL) communication. For example, LTE TDD configuration 1 supportsDSUUDDSUUD which provides that LTE subframe numbers 0, 4, 5 and 9 can beused for DL communication, subframe numbers 2, 3, 7 and 8 can be usedfor UL communication, and subframe numbers 1 and 6 are reserved forspecial frames.

As shown in FIG. 1, Donor CBSD z 150 may serve many CBRS RNs (160, 170)in a given area and each such CBRS RN may have a different type ofrequirement for TDD frame format, depending on the traffic requirementsof the UEs that each CBRS RN is serving. For example, some RNs may havehigher DL traffic while some other RNs may have higher UL traffic. SinceDonor CBSD z 150 chooses its own TDD frame format, incompatible TDDframe formats may result for some devices (i.e., RNs or UEs), thusdegrading their performance by, e.g., increasing latency or evendegrading overall throughput.

In another scenario, if a given CBRS RN is assigned a same frequency onboth of its air-interfaces and if it is a half-duplex CBRS RN,performance may be degraded.

Embodiments described herein provide approaches to appropriatelyallocate resources to CBRS RNs, 160, 170.

Approach I: Resource Allocation for CBSD of CBRS RN

FIG. 2 is a ladder diagram depicting a series of operations forallocating resources to a CBSD of CBRS RN in accordance with an exampleembodiment. At 201, Donor CBSD z 150 registers with SAS 110. As part ofan initial set-up procedure, SAS 110 grants assigned resources to DonorCBSD z 150 (e.g., channel, max EIRP, . . . ). At 202, Donor CBSD z 150starts communicating with CBRS UEs, including CBRS UE y 171 of CBRS RN y170. At 203, CBRS UE y 171 (of CBRS RN y 170) detects that it hasconnectivity to Donor CBSD z 150, and as such informs CBSD y 172 of suchconnectivity.

In response to being informed of the connectivity with Donor CBSD z 150,at 204A and 204B, CBSD y 172 sends a message to Donor CBSD z 150indicating that it is a CBRS RN and is looking for resources to beassigned to it. This message can be conveyed, e.g., by enhancing the LTERRC (Radio Resource Control) protocol for CBRS RNs. As part of thismessage, CBRS UE y 171 conveys parameters needed for registration withSAS 110 such as CBSD serial number, CBSD category, location, etc. ofCBSD y 172. In addition, CBSD y 172 identifies the type of RN it is,namely, Basic Type I, Type IA, Type D3 or Type II, inband or outband,half-duplex or full-duplex or a RN with multiple types of capabilities(e.g., Type I and II).

At 205, Donor CBSD z 150 continues its normal operation but, inaccordance with an example embodiment, sends a new registration requestfor RN message, i.e., “RNRegistrationRequest,” to SAS 110 with relevantparameters. In the event there are multiple CBRS RNs that are to beregistered, Donor CBSD z 150 can send all such requests in a samemessage to SAS 110.

From operation 205, SAS 110 learns that there is at least one CBRS RNcommunicating via Donor CBSD z 150 and also learns the relevantparameters for such relay nodes. In response to receiving thatinformation, at 206, SAS 110 sends a “RNRegistrationResponse” message,indicating that registration has been successful.

At 207A, 207B, Donor CBSD z 150 informs CBSD y 172 that registrationwith SAS 110 was successful. At 208, SAS 110 communicates with CBSD y172 using SAS-CBSD procedures, just like SAS 110 might communicate withDonor CBSD z 150. SAS 110 may also establish a security association witheach RN, in this case CBRS RN y 170.

At 209, SAS 110 (i.e., resource allocation logic 105) performs enhancedresource allocation taking into account the presence of CBRS RN y 170(and any other CBRS RNs). For example, SAS 110 considers specificparameters such as capabilities of CBRS RN y 170 (as indicated earlier),location of the CBRS RN, measurement reports and various otherparameters while deciding about resources to be allocated to each CBRSRN.

At 210, Donor CBSD z 150 forwards a grant response for CBSD y 172including, e.g., Channel id, max EIRP, etc. Once successfully processed,suitable channels along with the max EIRP permitted can be implementedby CBSD y 172. CBSD y 172 can then start using these channels tocommunicate with CBRS UE y1 that is communicating with CBRS RN y 170.

Approach II: SAS Changes Allocated Resources for a CBRS when CBRS RNsare Active in the Network

Reference is now made to FIG. 3, which shows a CBRS network topology 300and resource allocation logic in accordance with an example embodiment.It is quite possible that SAS 110 might have a need to change channelsallocated to Donor CBSD z 150. However, as SAS 110 changes channels forDonor CBSD z 150, interference on CBRS RNs 320, 330, 340, 350 can changedrastically. For example, Donor CBSD z 150 could be using channel c1 tocommunicate with CBRS UEs (including UEs functions CBRS UE r1, CBRS UEr2, CBRS UE r3, CBRS UE r4 of CBRS RNs 320, 330, 340, 350 thatcommunicate with Donor CBSD z 150).

Assume that there are four CBRS RNs 320, 330, 340, 350 in a given areaand Donor CBSD z 150 initially assigned channel ids c2, c3, c4, c2 (i.e.r1:c2, r2:c3, r3:c4, r4:c2). Now, suppose SAS 110 needs to change thechannel of Donor CBSD z 150 from c1 to c2. Such a change might createinterference at two CBRS RNs 320, 350 (i.e. r1 and r4) since, in thisexample, the CBSDs of those RNs were initially assigned channel c2 forcommunication with their UEs. It is also possible that some of theseCBRS RNs are not equipped to handle this interference (e.g., they areoutband CBRS RNs only). This scenario is addressed as follows, and withreference to FIG. 4, which is a flow chart depicting a series ofoperations for handling channel changes for a Donor CBSD thatcommunicates with CBRS RNs.

At 410, SAS 110 determines to change a channel allocated to Donor CBSD z150 (e.g. from c1 to c2 in this example). At 412, instead of directlychanging the channel for Donor CBSD z 150, SAS 110 considers the CBRSRNs that are communicating via this (or near-by) Donor CBRS z 150 andconsiders parameters such as channels used by such CBRS RNs (e.g., 320,330, 340, 350) (for their CBSDs), type of RN (or capabilities in termsof inband/outband/HD/FD, Type 1/2, etc.) and other relevant parameters.

At 414, SAS 110 undertakes channel management optimization based on theforegoing factors and determines whether the performance of one or moreCBRS RNs will be degraded if resources are changed for the Donor CBSD.For example, SAS 110 can determine whether changing the channel forDonor CBSD z 150 (e.g., from c1 to c2) is going to increase interferencefor selected RNs (e.g., r1 and r4 in the instant example) and some ofthese RNs (e.g., r4) do not have the capability to handle suchinterference (e.g., if RN r4 is an outband type of RN and cannot handleinband transmissions). If no such interference is expected, then at 416,SAS 110 can change the resource allocation for Donor CBSD 150 withoutfurther changes.

On the other hand, if performance of one or more of the CBRS RNs will bedegraded, then, at 418, SAS 110 changes the resource allocation for boththe Donor CBSD and impacted CBRS RNs.

FIG. 5 is a ladder diagram depicting a series of operations for ascenario in which SAS changes allocated resources for a Donor CBRS and aCBRS RN in accordance with an example embodiment. As shown in thedrawing, Donor CBSD z 150 initially communicates via channel c1, CBRS RN350 communicates via channel c2, CBRS RN 340 communicates via channelc4, CBRS RN 330 communicates via channel c3, and CBRS RN 320communicates via channel c2. As a result of the optimization performedby SAS 110 (i.e., resource allocation logic 105) regarding interference,SAS 110 determines that resources for Donor CBSD z 150 and CBRS RN 350are to be changed, whereas the resource allocation for CBRS RNs 320,330, and 340 should remain unchanged. As a result, at 510, instructionsto that effect are transmitted to Donor CBSD z 150. At 512, Donor CBSD z150 communicates a resource change from channel c2 to channel c5 to CBRSRN 350, and at 514 the resources of the remaining CBRS RNs 320, 330, and340 are indicated as not changing. At 516, Donor CBSD z 150 changes itschannel from c1 to channel c2.

Approach III: SAS Changes Allocated Resources for a CBRS Relay Node

In a similar vein, if SAS 110 wants to change resources (channel, maxEIRP, . . . ) for a given CBRS RN, SAS 110 may consider (i) resourcesused by Donor CBSD z 150 and other CBRS RNs in that area, (ii)capabilities of the given CBRS RN and other CBRS RNs in that area, and(iii) other relevant parameters to make a decision to minimizeinterference and optimize performance in that network. Such a decisioncould involve changing resources not only for the given CBRS RN but alsofor Donor CBSD z 150 and other CBRS RNs in that area.

Reference is made to FIG. 6, which is a flow chart depicting a series ofoperations for handling channel changes for a CBRS RN in accordance withan example embodiment, and to FIG. 7, which is a ladder diagramdepicting a series of operations for a scenario in which a SAS changesallocated resources for a given CBRS RN in accordance with an exampleembodiment.

Assume, in this case, that Donor CBSD z 150 is using channel c1, CBSD r1of CBRS RN r1 320 is using c2, CBSD r2 of RN r2 330 is using c3, CBSD r3of RN r3 340 is using c4, and CBSD r4 of RN r4 350 is using c2. In eachcase, maxEIRP is also assigned by SAS 110.

Assume that SAS 110 determines, at 610, to change resources for CBSD r4(of CBRS RN r4 350) from (c2, . . . ) to (c1, . . . ). If SAS 110proceeds with such a resource change resources for CBSD r4 of RN r4 350in this way, this can create performance issues for CBRS RN r4 350 asthat given RN may not have the capability to handle the same channel onboth of its air-interfaces. As such, at 612, SAS 110 considers resourcesbeing used by donor CBSD z 150 and other relay nodes. At 614, SAS 110determines whether the performance of the given RN or other RNs may bedegraded in view of the proposed change of resources. If no degradationis expected, then at 616, SAS changes the resources assigned to thegiven RN as initially proposed or intended. On the other hand, if adegradation is expected, then at 618, SAS 110 changes resources forimpacted RNs (and even for the Donor CBSD as might be necessary).

The foregoing approach is shown in FIG. 7, where, at 705, SAS 110undertakes an optimization with regard to resource allocation, anddetermines to change resources for Donor CBSD z 150 and CBSD r4 (CBRS RN350), and to maintain or keep the same resources for the remaining CBRSRNs 320, 330, 340, as indicated. At 710, SAS 110 communicates with DonorCBSD z 150 accordingly. At 712, Donor CBSD z 150 communicates with CBSDRN 350 to change its channel to channel c1. At 714, Donor CBSD z 150 maydo nothing or re-confirm that the remaining CBRS RNs 320, 330, 340 keepthe same or prior resources. At 716, Donor CBSD z 150 changes itschannel from channel c1 to channel c6.

Approach IV: Resource Optimization Using CBRS-Analytics Module at DNA-C

FIG. 8 shows a CBRS network topology 800 that leverages a digitalnetwork application controller (DNA-C) (or simply “external controller”)810 to provide resource allocation logic in accordance with an exampleembodiment. As shown, external controller 810 is in communication withCBRS RNs 160 and 170 via links 820, 830, respectively, which run throughDonor CBSD z 150. External controller 810 is also in communication withDonor CBSD z 150 via link 840. With such links, CBRS RN and Donor CBSD z150 capabilities along with other network topology and performanceparameters can be provided to external controller 810. In such animplementation, SAS 110 might be considered to have a higher level viewof the CBRS network 800 in a given area, while external controller 810might have a more complete view of the network within an enterprise. Asa result, external controller 810, and specifically CBRS—analytics &performance optimization logic 812, first estimates/considers/determinesresources to be assigned to CBRS RNs 160, 170 and Donor CBSD z 150 inconnection with initial resource allocation and subsequent proposedchanges to resource allocation. Resulting suggestions or recommendationsgenerated by external controller 810 may be provided to SAS 110 via link850, (along, in one possible embodiment, with an indication as to ajustification for such suggestions or recommendations) via Donor CBSD z150. SAS 110 may then consider the suggestions along with otherparameters in making final resource management decisions.

Approach V: Selection of Suitable LTE-TDD Frame Configurations for CBRSRNs and Donor CBSD

FIG. 9 shows a CBRS network topology 900 that leverages a DNA-C (orexternal controller) 910 that hosts CBRS analytics & performanceoptimization logic 912 to provide additional resource allocation logicin accordance with an example embodiment. As discussed earlier, aLTE-TDD base station uses a LTE-TDD format that consists of a pattern ofslots for DL and UL communication. For example, LTE TDD configuration 1supports DSUUDDSUUD where LTE subframe numbers 0, 4, 5 and 9 can be usedfor DL communication, subframe numbers 2, 3, 7 and 8 can be used for ULcommunication, and subframe numbers 1 and 6 are reserved for specialframes.

As shown in FIG. 9, Donor CBSD z 150 could be serving many CBRS RNs 160,170 in an area, and each such CBRS RN may have a different type ofrequirement for its LTE-TDD frame format. For example, one CBRS RN-UEpair may have higher DL traffic compared to another CBRS RN-UE pair,which may have higher UL traffic. As each Donor CBSD chooses its own TDDframe format, this can lead to incompatible TDD frame formats for somedevices (e.g., RNs or UEs) thereby degrading their performance. Forexample, latency may increase for some UEs and throughput may bedegraded.

To address this issue, and in accordance with an embodiment, externalcontroller 910 collects and analyzes a variety of parameters from UEs(such as downlink and uplink throughput, type of applications running oneach UE—e.g. downlink latency sensitive, uplink latency sensitive, besteffort only etc.) and CBRS RNs via links 920, 930 (and from Donor CBSD z150 via link 940). The LTE-TDD frame format used by Donor CBSD z 150 isalso provided to external controller 910. This information is analyzedby external controller 910 and suitable LTE-TDD frame formatconfigurations are selected and communicated to Donor CBSD z 150 andCBRS RNs 160, 170 (e.g., LTE-TDD frame format h(x), LTE-TDD frame formath(y), LTE-TDD frame format h(z)). Note that some 3GPP releases do notallow a change to a TDD frame configuration at any arbitrary time. Insuch scenarios, it is possible to change frame formats at the same timeas changing channel resources as described above.

In accordance with a different embodiment, it is possible that a DonorCBSD allocates resources for CBRS RNs. In this case, it is possible tofurther enhance the Donor CBSD-SAS registration procedure wherein theDonor CBSD can optionally indicate a presence of RNs and ask for a poolof channels (along with max EIRP for each such channel). The Donor CBSDmay then allocate resources to the CBRS RNs. These resource allocationsmay be communicated to the CBRS RNs by appropriately enhancing LTE RRCmessages. If all CBRS RNs support in-band operation, the Donor CBSDcould potentially use same the channel for all CBRS RNs. The Donor CBSDmight also offload this function to external controller (e.g., 910).

In the above described embodiment, a Donor CBSD may be considered to befunctioning as a “mini-SAS”, but may only have a limited view of thenetwork. As such, it may be more desirable to have external controller(e.g., 910) perform this functionality due to its more central view ofthe network and thus its knowledge of information regarding the DonorCBSD, CBRS RNs and UEs.

In sum, as CBRS access points get deployed, it becomes important toenhance coverage and capacity for cell edge (and other) users. Asdescribed herein, LTE (e.g., CBRS) relay nodes are used to provideenhanced coverage and capacity in such scenarios, and approaches areprovided that help to reduce interference in CBRS networks.

FIG. 10 is a flow chart depicting a series of operations for allocatingresources in a CBRS network having CBRS RNs in accordance with anexample embodiment. The operations are described as being performed by aSAS, but those skilled in the art will appreciate that another device(e.g., a controller such as external controller 810 or 910) may alsoperform some or all of these operations. At 1002, a SAS receives, from aDonor citizens broadband radio service (CBRS) base station device(CBSD), a registration request, the registration request includingcapabilities information about a CBRS Relay Node with which the DonorCBSD communicates. At 1004, in response to the registration request, theSAS sends to the Donor CBSD, a registration response indicatingsuccessful registration of the CBRS Relay Node. At 1006, in response tothe registration response, the SAS receives via the Donor CBSD aspectrum enquiry message from the CBRS Relay Node seeking a channelallocation. And, at 1008, and in response to the spectrum enquirymessage, the SAS sends, via the Donor CBSD, a resource grant response tothe CBRS Relay Node, wherein the resource grant response includes anallocated channel and a maximum Equivalent Isotropically Radiated Power(EIRP) for the allocated channel.

FIG. 11 depicts a device 1100 (e.g., a SAS or external controller) thatexecutes resource allocation logic 105 in accordance with an exampleembodiment. It should be appreciated that FIG. 11 provides only anillustration of one embodiment and does not imply any limitations withregard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be made.Indeed, in many implementations of a SAS or external controllerconfigured to host resource allocation logic 105, much of the hardwaredescribed below may not be needed.

As depicted, the device 1100 includes a bus 1112, which providescommunications between computer processor(s) 1114, memory 1116,persistent storage 1118, communications unit 1120, and input/output(I/O) interface(s) 1122. Bus 1112 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as microprocessors, communications and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, bus 1112 can beimplemented with one or more buses.

Memory 1116 and persistent storage 1118 are computer readable storagemedia. In the depicted embodiment, memory 1116 includes random accessmemory (RAM) 1124 and cache memory 1126. In general, memory 1116 caninclude any suitable volatile or non-volatile computer readable storagemedia. Instructions for the “resource allocation logic” may be stored inmemory 1116 or persistent storage 1118 for execution by processor(s)1114.

One or more programs may be stored in persistent storage 1118 forexecution by one or more of the respective computer processors 1114 viaone or more memories of memory 1116. The persistent storage 1118 may bea magnetic hard disk drive, a solid state hard drive, a semiconductorstorage device, read-only memory (ROM), erasable programmable read-onlymemory (EPROM), flash memory, or any other computer readable storagemedia that is capable of storing program instructions or digitalinformation.

The media used by persistent storage 1118 may also be removable. Forexample, a removable hard drive may be used for persistent storage 1118.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage1118.

Communications unit 1120, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 1120 includes one or more network interface cards.Communications unit 1120 may provide communications through the use ofeither or both physical and wireless communications links.

I/O interface(s) 1122 allows for input and output of data with otherdevices that may be connected to computer device 1100. For example, I/Ointerface 1122 may provide a connection to external devices 1128 such asa keyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 1128 can also include portable computerreadable storage media such as database systems, thumb drives, portableoptical or magnetic disks, and memory cards.

Software and data used to practice embodiments can be stored on suchportable computer readable storage media and can be loaded ontopersistent storage 1118 via I/O interface(s) 1122. I/O interface(s) 1122may also connect to a display 1130. Display 1130 provides a mechanism todisplay data to a user and may be, for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment. However, itshould be appreciated that any particular program nomenclature herein isused merely for convenience, and thus the embodiments should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

Data relating to operations described herein may be stored within anyconventional or other data structures (e.g., files, arrays, lists,stacks, queues, records, etc.) and may be stored in any desired storageunit (e.g., database, data or other repositories, queue, etc.). The datatransmitted between entities may include any desired format andarrangement, and may include any quantity of any types of fields of anysize to store the data. The definition and data model for any datasetsmay indicate the overall structure in any desired fashion (e.g.,computer-related languages, graphical representation, listing, etc.).

The present embodiments may employ any number of any type of userinterface (e.g., Graphical User Interface (GUI), command-line, prompt,etc.) for obtaining or providing information (e.g., data relating toscraping network sites), where the interface may include any informationarranged in any fashion. The interface may include any number of anytypes of input or actuation mechanisms (e.g., buttons, icons, fields,boxes, links, etc.) disposed at any locations to enter/displayinformation and initiate desired actions via any suitable input devices(e.g., mouse, keyboard, etc.). The interface screens may include anysuitable actuators (e.g., links, tabs, etc.) to navigate between thescreens in any fashion.

The environment of the present embodiments may include any number ofcomputer or other processing systems (e.g., client or end-user systems,server systems, etc.) and databases or other repositories arranged inany desired fashion, where the present embodiments may be applied to anydesired type of computing environment (e.g., cloud computing,client-server, network computing, mainframe, stand-alone systems, etc.).The computer or other processing systems employed by the presentembodiments may be implemented by any number of any personal or othertype of computer or processing system (e.g., desktop, laptop, PDA,mobile devices, etc.), and may include any commercially availableoperating system and any combination of commercially available andcustom software (e.g., machine learning software, etc.). These systemsmay include any types of monitors and input devices (e.g., keyboard,mouse, voice recognition, etc.) to enter and/or view information.

It is to be understood that the software of the present embodiments maybe implemented in any desired computer language and could be developedby one of ordinary skill in the computer arts based on the functionaldescriptions contained in the specification and flow charts illustratedin the drawings. Further, any references herein of software performingvarious functions generally refer to computer systems or processorsperforming those functions under software control. The computer systemsof the present embodiments may alternatively be implemented by any typeof hardware and/or other processing circuitry.

Each of the elements described herein may couple to and/or interact withone another through interfaces and/or through any other suitableconnection (wired or wireless) that provides a viable pathway forcommunications. Interconnections, interfaces, and variations thereofdiscussed herein may be utilized to provide connections among elementsin a system and/or may be utilized to provide communications,interactions, operations, etc. among elements that may be directly orindirectly connected in the system. Any combination of interfaces can beprovided for elements described herein in order to facilitate operationsas discussed for various embodiments described herein.

The various functions of the computer or other processing systems may bedistributed in any manner among any number of software and/or hardwaremodules or units, processing or computer systems and/or circuitry, wherethe computer or processing systems may be disposed locally or remotelyof each other and communicate via any suitable communications medium(e.g., LAN, WAN, Intranet, Internet, hardwire, modem connection,wireless, etc.). For example, the functions of the present embodimentsmay be distributed in any manner among the various end-user/client andserver systems, and/or any other intermediary processing devices. Thesoftware and/or algorithms described above and illustrated in the flowcharts may be modified in any manner that accomplishes the functionsdescribed herein. In addition, the functions in the flow charts ordescription may be performed in any order that accomplishes a desiredoperation.

The software of the present embodiments may be available on anon-transitory computer useable medium (e.g., magnetic or opticalmediums, magneto-optic mediums, floppy diskettes, CD-ROM, DVD, memorydevices, etc.) of a stationary or portable program product apparatus ordevice for use with stand-alone systems or systems connected by anetwork or other communications medium.

The communication network may be implemented by any number of any typeof communications network (e.g., LAN, WAN, Internet, Intranet, VPN,etc.). The computer or other processing systems of the presentembodiments may include any conventional or other communications devicesto communicate over the network via any conventional or other protocols.The computer or other processing systems may utilize any type ofconnection (e.g., wired, wireless, etc.) for access to the network.Local communication media may be implemented by any suitablecommunication media (e.g., local area network (LAN), hardwire, wirelesslink, Intranet, etc.).

The system may employ any number of any conventional or other databases,data stores or storage structures (e.g., files, databases, datastructures, data or other repositories, etc.) to store information. Thedatabase system may be implemented by any number of any conventional orother databases, data stores or storage structures (e.g., files,databases, data structures, data or other repositories, etc.) to storeinformation. The database system may be included within or coupled tothe server and/or client systems. The database systems and/or storagestructures may be remote from or local to the computer or otherprocessing systems, and may store any desired data.

The present embodiments may employ any number of any type of userinterface (e.g., Graphical User Interface (GUI), command-line, prompt,etc.) for obtaining or providing information (e.g., data relating toproviding enhanced delivery options), where the interface may includeany information arranged in any fashion. The interface may include anynumber of any types of input or actuation mechanisms (e.g., buttons,icons, fields, boxes, links, etc.) disposed at any locations toenter/display information and initiate desired actions via any suitableinput devices (e.g., mouse, keyboard, etc.). The interface screens mayinclude any suitable actuators (e.g., links, tabs, etc.) to navigatebetween the screens in any fashion.

The embodiments presented may be in various forms, such as a system, amethod, and/or a computer program product at any possible technicaldetail level of integration. The computer program product may include acomputer readable storage medium (or media) having computer readableprogram instructions thereon for causing a processor to carry outaspects of presented herein.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present embodiments may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Python, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects presented herein.

Aspects of the present embodiments are described herein with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to the embodiments.It will be understood that each block of the flowchart illustrationsand/or block diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerreadable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments. In this regard, each block in the flowchart or blockdiagrams may represent a module, segment, or portion of instructions,which comprises one or more executable instructions for implementing thespecified logical function(s). In some alternative implementations, thefunctions noted in the blocks may occur out of the order noted in thefigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. It will also be noted that each block of the block diagramsand/or flowchart illustration, and combinations of blocks in the blockdiagrams and/or flowchart illustration, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts or carry out combinations of special purpose hardware and computerinstructions.

In summary, in one form, a method is provided. The method includes at aspectrum access system, receiving, from a Donor citizens broadband radioservice (CBRS) base station device (CBSD), a registration request, theregistration request including capabilities information about a CBRSRelay Node with which the Donor CBSD communicates; in response to theregistration request, sending, from the spectrum access system to theDonor CBSD, a registration response indicating successful registrationof the CBRS Relay Node; in response to the registration response,receiving via the Donor CBSD a spectrum enquiry message from the CBRSRelay Node seeking a channel allocation from the spectrum access system;and in response to the spectrum enquiry message, sending from thespectrum access system, and via the Donor CBSD, a resource grantresponse to the CBRS Relay Node, wherein the resource grant responseincludes an allocated channel and a maximum Equivalent IsotropicallyRadiated Power (EIRP) for the allocated channel.

In an embodiment, the capabilities information about the CBRS Relay Nodemay include an indication of a location of the CBRS Relay Node and anindication of a type of the CBRS Relay Node.

In one embodiment, the indication of the type of the CBRS Relay Node mayinclude an indication regarding whether the CBRS Relay Node is an inbandrelay node or an outband relay node.

In another embodiment, the method includes selecting the allocatedchannel and maximum EIRP based on the location of the CBRS Relay Nodeand the type of the CBRS Relay Node.

In still another embodiment, the method includes the spectrum accesssystem determining that an allocated channel for the Donor CBSD shouldbe changed; and the spectrum access system determining whether aproposed new channel for the Donor CBSD will cause interference with theCBRS Relay Node.

The method may still further include, when the spectrum access systemdetermines that the proposed new channel for the Donor CBSD will causeinterference with the CBRS Relay Node, providing a new allocatedchannel, respectively, to the Donor CBSD and to the CBRS Relay Node.

The method may still further include the spectrum access systemdetermining that the allocated channel for the CBRS Relay Node should bechanged; and the spectrum access system determining whether a proposednew channel for the CBRS Relay Node will cause interference for the CBRSRelay Node or for another CBRS Relay Node.

In an embodiment, the method may include when the spectrum access systemdetermines that the proposed new channel for the CBRS Relay Node willcause interference for the CBRS Relay Node or for another CBRS RelayNode, providing a new allocated channel, respectively, to the Donor CBSDand to the CBRS Relay Node

In still another embodiment, the method may include receiving from anexternal controller, at the spectrum access system, a recommendationregarding how to allocate channels to the Donor CBSD and to the CBRSRelay Node.

And, the method may also include selecting a time division duplex (TDD)format for the CBRS Relay Node.

In another form, a device may also be provided in accordance with anembodiment. The device may include an interface unit configured toenable network communications; a memory; and one or more processorscoupled to the interface unit and the memory, and configured to:receive, from a Donor citizens broadband radio service (CBRS) basestation device (CBSD), a registration request, the registration requestincluding capabilities information about a CBRS Relay Node with whichthe Donor CBSD communicates; in response to the registration request,send to the Donor CBSD, a registration response indicating successfulregistration of the CBRS Relay Node; in response to the registrationresponse, receive via the Donor CBSD a spectrum enquiry message from theCBRS Relay Node seeking a channel allocation; and in response to thespectrum enquiry message, send, via the Donor CBSD, a resource grantresponse to the CBRS Relay Node, wherein the resource grant responseincludes an allocated channel and a maximum Equivalent IsotropicallyRadiated Power (EIRP) for the allocated channel.

In an embodiment, the capabilities information about the CBRS Relay Nodemay include an indication of a location of the CBRS Relay Node and anindication of a type of the CBRS Relay Node.

In an embodiment, the indication of the type of the CBRS Relay Node mayinclude an indication regarding whether the CBRS Relay Node is an inbandrelay node or an outband relay node.

In an embodiment the one or more processors may be configured to selectthe allocated channel and maximum EIRP based on the location of the CBRSRelay Node and the type of the CBRS Relay Node.

In an embodiment the one or more processors may be configured todetermine that an allocated channel for the Donor CBSD should bechanged; and determine whether a proposed new channel for the Donor CBSDwill cause interference with the CBRS Relay Node.

In an embodiment the one or more processors may be configured to when itis determined that the proposed new channel for the Donor CBSD willcause interference with the CBRS Relay Node, provide a new allocatedchannel, respectively, to the Donor CBSD and to the CBRS Relay Node.

In an embodiment the one or more processors may be configured todetermine that the allocated channel for the CBRS Relay Node should bechanged; and determine whether a proposed new channel for the CBRS RelayNode will cause interference for the CBRS Relay Node or for another CBRSRelay Node.

In an embodiment the one or more processors may be configured to when itis determined that the proposed new channel for the CBRS Relay Node willcause interference for the CBRS Relay Node or for another CBRS RelayNode, provide a new allocated channel, respectively, to the Donor CBSDand to the CBRS Relay Node.

In still another form, a non-transitory computer readable storage mediais provided that is encoded with instructions that, when executed by aprocessor, cause the processor to receive, from a Donor citizensbroadband radio service (CBRS) base station device (CBSD), aregistration request, the registration request including capabilitiesinformation about a CBRS Relay Node with which the Donor CBSDcommunicates; in response to the registration request, send to the DonorCBSD, a registration response indicating successful registration of theCBRS Relay Node; in response to the registration response, receive viathe Donor CBSD a spectrum enquiry message from the CBRS Relay Nodeseeking a channel allocation; and in response to the spectrum enquirymessage, send, via the Donor CBSD, a resource grant response to the CBRSRelay Node, wherein the resource grant response includes an allocatedchannel and a maximum Equivalent Isotropically Radiated Power (EIRP) forthe allocated channel.

In this form, the capabilities information about the CBRS Relay Node mayinclude an indication of a location of the CBRS Relay Node and anindication of a type of the CBRS Relay Node.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments disclosed. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the described embodiments. The terminologyused herein was chosen to best explain the principles of theembodiments, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method comprising: at a resource allocationsystem, receiving, from a Donor wireless base station device, aregistration request, the registration request including capabilitiesinformation about a Relay Node with which the Donor wireless basestation device communicates; in response to the registration request,sending, from the resource allocation system to the Donor wireless basestation device, a registration response indicating successfulregistration of the Relay Node; in response to the registrationresponse, receiving via the Donor wireless base station device aspectrum enquiry message from the Relay Node seeking a channelallocation from the resource allocation system; and in response to thespectrum enquiry message, sending from the resource allocation system,and via the Donor wireless base station device, a resource grantresponse to the Relay Node, wherein the resource grant response includesan allocated channel.
 2. The method of claim 1, wherein the capabilitiesinformation about the Relay Node comprises an indication of a locationof the Relay Node and an indication of a type of the Relay Node.
 3. Themethod of claim 2, wherein the indication of the type of the Relay Nodeincludes an indication regarding whether the Relay Node is an inbandrelay node or an outband relay node.
 4. The method of claim 3, furthercomprising selecting the allocated channel based on the location of theRelay Node and the type of the Relay Node.
 5. The method of claim 1,further comprising: the resource allocation system determining that anallocated channel for the Donor wireless base station device should bechanged; and the resource allocation system determining whether aproposed new channel for the Donor wireless base station device willcause interference with the Relay Node.
 6. The method of claim 5,further comprising: when the resource allocation system determines thatthe proposed new channel for the Donor wireless base station device willcause interference with the Relay Node, providing a new allocatedchannel, respectively, to the Donor wireless base station device and tothe Relay Node.
 7. The method of claim 1, further comprising: theresource allocation system determining that the allocated channel forthe Relay Node should be changed; and the resource allocation systemdetermining whether a proposed new channel for the Relay Node will causeinterference for the Relay Node or for another Relay Node.
 8. The methodof claim 7, further comprising: when the resource allocation systemdetermines that the proposed new channel for the Relay Node will causeinterference for the Relay Node or for another Relay Node, providing anew allocated channel, respectively, to the Donor wireless base stationdevice and to the Relay Node.
 9. The method of claim 1, furthercomprising, receiving from an external controller, at the resourceallocation system, a recommendation regarding how to allocate channelsto the Donor wireless base station device and to the Relay Node.
 10. Themethod of claim 1, further comprising, selecting a time division duplex(TDD) format for the Relay Node.
 11. A device comprising: an interfaceunit configured to enable network communications; a memory; and one ormore processors coupled to the interface unit and the memory, andconfigured to: receive, from a Donor wireless base station device, aregistration request, the registration request including capabilitiesinformation about a Relay Node with which the Donor wireless basestation device communicates; in response to the registration request,send to the Donor wireless base station device, a registration responseindicating successful registration of the Relay Node; in response to theregistration response, receive via the Donor wireless base stationdevice a spectrum enquiry message from the Relay Node seeking a channelallocation; and in response to the spectrum enquiry message, send, viathe Donor wireless base station device, a resource grant response to theRelay Node, wherein the resource grant response includes an allocatedchannel.
 12. The device of claim 11, wherein the capabilitiesinformation about the Relay Node comprises an indication of a locationof the Relay Node and an indication of a type of the Relay Node.
 13. Thedevice of claim 12, wherein the indication of the type of the Relay Nodeincludes an indication regarding whether the Relay Node is an inbandrelay node or an outband relay node.
 14. The device of claim 13, whereinthe one or more processors are further configured to select theallocated channel based on the location of the Relay Node and the typeof the Relay Node.
 15. The device of claim 13, wherein the one or moreprocessors are further configured to: determine that an allocatedchannel for the Donor wireless base station device should be changed;and determine whether a proposed new channel for the Donor wireless basestation device will cause interference with the Relay Node.
 16. Thedevice of claim 15, wherein the one or more processors are furtherconfigured to: when it is determined that the proposed new channel forthe Donor wireless base station device will cause interference with theRelay Node, provide a new allocated channel, respectively, to the Donorwireless base station device and to the Relay Node.
 17. The device ofclaim 11, wherein the one or more processors are further configured to:determine that the allocated channel for the Relay Node should bechanged; and determine whether a proposed new channel for the Relay Nodewill cause interference for the Relay Node or for another Relay Node.18. The device of claim 17, wherein the one or more processors arefurther configured to: when it is determined that the proposed newchannel for the Relay Node will cause interference for the Relay Node orfor another Relay Node, provide a new allocated channel, respectively,to the Donor wireless base station device and to the Relay Node.
 19. Anon-transitory computer readable storage media encoded with instructionsthat, when executed by a processor, cause the processor to: receive,from a Donor wireless base station device, a registration request, theregistration request including capabilities information about a RelayNode with which the Donor wireless base station device communicates; inresponse to the registration request, send to the Donor wireless basestation device, a registration response indicating successfulregistration of the Relay Node; in response to the registrationresponse, receive via the Donor wireless base station device a spectrumenquiry message from the Relay Node seeking a channel allocation; and inresponse to the spectrum enquiry message, send, via the Donor wirelessbase station device, a resource grant response to the Relay Node,wherein the resource grant response includes an allocated channel. 20.The non-transitory computer readable storage media of claim 19, whereinthe capabilities information about the Relay Node comprises anindication of a location of the Relay Node and an indication of a typeof the Relay Node.